<!DOCTYPE html>
<!--
  ~ Copyright (C) 2005 - 2019 Schlichtherle IT Services.
  ~ All rights reserved. Use is subject to license terms.
  -->
<html>
    <head>
        <title></title>
        <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    </head>
    <body>
        <p>
            New applications should start with
            <a href="global/namespace/truelicense/v2/json/V2Json.html"><code>global.namespace.truelicense.v2.json.V2Json</code></a>
            or
            <a href="global/namespace/truelicense/v2/xml/V2Xml.html"><code>global.namespace.truelicense.v2.xml.V2Xml</code></a>,
            depending on whether they want to use the Version-2-with-JSON (V2/JSON) or the Version-2-with-XML (V2/XML)
            license key format.
            The V2/JSON format produces smaller license keys.
            Generating V2/JSON format license keys is also faster than generating V2/XML format license keys (there is
            no notable difference on the license consumer side however).
            However, using V2/JSON format license keys requires the
            <a href="http://jackson.codehaus.org">Jackson JSON Processor</a>
            to be present on the class path at runtime.
        <p>
            Applications which need to use license keys which have been generated by TrueLicense 1 need to use the
            Version-1 (V1) format in
            <a href="global/namespace/truelicense/v1/V1.html"><code>global.namespace.truelicense.v1.V1</code></a>.
        </p>
    </body>
</html>
